Resolve #7874 - stop too many fetch calls to docmanager-extension on … #7879
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for #7874, to stop too many fetch calls to docmanager-extension. This happens as there is a change event that gets emit from a forEach loop. All requests info are the same and the response received is the same which make the calls to be redundant. So the fix is to restrict the number of calls to 1.
References
#7874
Code changes
Code change is to register a callback that does not trigger a reload (fetch call) when an existing promise is already pending. The promise is tracked by maintaining a promisePending boolean flag. This ensures that even when multiple change events are emitted from a loop, it'll avoid creating multiple promises which ends up in redundant requests.
User-facing changes
Backwards-incompatible changes
No
Before Fix Network Log
After Fix Network Log